ATREE FOR WINDOWS release 2.7 ~~~~~ ~~~ ~~~~~~~ ~~~~~~~ ~~~ With release 2.7, lfbatch.exe has been done away with. Lfedit will process and run all .lf files, but will only allow editing of files that are 48K or less, due to Windows 3.x limitations of multiline edit controls. Use another editor to edit .LF files bigger than 48K. With release 2.6 the atree.txt file has been replaced by a Windows help file, atree.hlp. All documentation can be found in atree.hlp. You can access it directly by running "winhelp atree.hlp". With release 2.51 a setup program has been included to set up a Windows Program Manager group. Please run setup.exe. With release 2.0 the atree.dll has been eliminated... please delete it from your Windows directory if you have a previous version of the software. The atree software was originally developed on UNIX, and this is the maintenenace release to the second attempt to port it to a PC architecture. Needless to say, the advanced memory capabilities of Windows has resulted in a much better product than the (now defunct) plain DOS version. Support for the Windows implementation of the atree software can be obtained by contacting Monroe Thomas at one of the two following addresses: Internet: monroe@cs.UAlberta.CA Compuserve: 70524,334 Please note that limited help will be given to Windows programming itself, and that all development was done using Borland C++ 3.x, so we can't answer questions relating to the Microsoft Windows SDK. All questions or suggestions pertaining to the implementation of the atree library in Windows are more than welcome. For expert advice and explanation on the theory behind Adaptive Logic Networks, you can contact Bill Armstrong on the Internet at arms@cs.UAlberta.CA. Thanks to everyone out there that has tried out the software. We're slowly killing backprop: with several promising results in meat classification, multiple regression, high speed particle classification, and prosthetic control, and more areas everyday, the world is learning the power of ALN's. We welcome your advice, questions, criticisms, as they help us to better serve the research community. M. Thomas 08/92